Dec 01 13:15:04.648 INFO testing juli1/rust-json-example against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 01 13:15:04.648 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 13:15:05.086 INFO [stdout] 218194da40be9ae571222bf1b13dc2e6fe7abd33f37476d22219a5a7b9709688
Dec 01 13:15:05.099 INFO running `"docker" "start" "-a" "218194da40be9ae571222bf1b13dc2e6fe7abd33f37476d22219a5a7b9709688"`
Dec 01 13:15:06.127 INFO [stderr] usermod: no changes
Dec 01 13:15:06.188 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 13:15:06.188 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 13:15:06.188 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 13:15:06.188 INFO [stderr] files will be included as a binary target:
Dec 01 13:15:06.188 INFO [stderr] 
Dec 01 13:15:06.188 INFO [stderr] * /source/src/main.rs
Dec 01 13:15:06.188 INFO [stderr] 
Dec 01 13:15:06.188 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 13:15:06.188 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 13:15:06.188 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 13:15:06.188 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 13:15:06.188 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 13:15:06.188 INFO [stderr] 
Dec 01 13:15:06.188 INFO [stderr] For more information on this warning you can consult
Dec 01 13:15:06.188 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 13:15:06.363 INFO [stderr]    Compiling tokio v0.0.0
Dec 01 13:15:06.375 INFO [stderr]    Compiling openssl v0.9.23
Dec 01 13:15:06.375 INFO [stderr]    Compiling http v0.1.4
Dec 01 13:15:06.375 INFO [stderr]    Compiling hyper v0.11.16
Dec 01 13:15:17.962 INFO [stderr]    Compiling native-tls v0.1.5
Dec 01 13:15:19.162 INFO [stderr]    Compiling tokio-tls v0.1.4
Dec 01 13:15:21.352 INFO [stderr]    Compiling hyper-tls v0.1.2
Dec 01 13:15:22.695 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Dec 01 13:15:28.712 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 22.56s
Dec 01 13:15:28.723 INFO [stderr] su: No module specific data is present
Dec 01 13:15:28.974 INFO running `"docker" "inspect" "218194da40be9ae571222bf1b13dc2e6fe7abd33f37476d22219a5a7b9709688"`
Dec 01 13:15:29.080 INFO running `"docker" "rm" "-f" "218194da40be9ae571222bf1b13dc2e6fe7abd33f37476d22219a5a7b9709688"`
Dec 01 13:15:29.188 INFO [stdout] 218194da40be9ae571222bf1b13dc2e6fe7abd33f37476d22219a5a7b9709688
Dec 01 13:15:29.193 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 13:15:29.367 INFO [stdout] 772ac5f01e22318ad808842de588fd5bf4bf1466d32dc52ef4491210eaf3deb3
Dec 01 13:15:29.368 INFO running `"docker" "start" "-a" "772ac5f01e22318ad808842de588fd5bf4bf1466d32dc52ef4491210eaf3deb3"`
Dec 01 13:15:29.816 INFO [stderr] usermod: no changes
Dec 01 13:15:29.848 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 13:15:29.848 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 13:15:29.848 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 13:15:29.848 INFO [stderr] files will be included as a binary target:
Dec 01 13:15:29.848 INFO [stderr] 
Dec 01 13:15:29.848 INFO [stderr] * /source/src/main.rs
Dec 01 13:15:29.848 INFO [stderr] 
Dec 01 13:15:29.848 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 13:15:29.848 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 13:15:29.848 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 13:15:29.848 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 13:15:29.848 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 13:15:29.848 INFO [stderr] 
Dec 01 13:15:29.848 INFO [stderr] For more information on this warning you can consult
Dec 01 13:15:29.848 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 13:15:29.963 INFO [stderr]    Compiling rust-json v0.1.0 (/source)
Dec 01 13:15:32.001 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.16s
Dec 01 13:15:32.011 INFO [stderr] su: No module specific data is present
Dec 01 13:15:32.385 INFO running `"docker" "inspect" "772ac5f01e22318ad808842de588fd5bf4bf1466d32dc52ef4491210eaf3deb3"`
Dec 01 13:15:32.481 INFO running `"docker" "rm" "-f" "772ac5f01e22318ad808842de588fd5bf4bf1466d32dc52ef4491210eaf3deb3"`
Dec 01 13:15:32.627 INFO [stdout] 772ac5f01e22318ad808842de588fd5bf4bf1466d32dc52ef4491210eaf3deb3
Dec 01 13:15:32.632 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 13:15:32.787 INFO [stdout] 229957bdf95003b8ff07cb79f602974a3e7db12e75dd6536e1c0cf40d5f7a413
Dec 01 13:15:32.790 INFO running `"docker" "start" "-a" "229957bdf95003b8ff07cb79f602974a3e7db12e75dd6536e1c0cf40d5f7a413"`
Dec 01 13:15:33.300 INFO [stderr] usermod: no changes
Dec 01 13:15:33.346 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 13:15:33.346 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 13:15:33.346 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 13:15:33.346 INFO [stderr] files will be included as a binary target:
Dec 01 13:15:33.346 INFO [stderr] 
Dec 01 13:15:33.346 INFO [stderr] * /source/src/main.rs
Dec 01 13:15:33.346 INFO [stderr] 
Dec 01 13:15:33.346 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 13:15:33.346 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 13:15:33.346 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 13:15:33.346 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 13:15:33.346 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 13:15:33.346 INFO [stderr] 
Dec 01 13:15:33.346 INFO [stderr] For more information on this warning you can consult
Dec 01 13:15:33.346 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 13:15:33.452 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Dec 01 13:15:33.457 INFO [stderr]      Running /target/debug/deps/specialized-176a8247941ac202
Dec 01 13:15:33.460 INFO [stdout] 
Dec 01 13:15:33.460 INFO [stdout] running 0 tests
Dec 01 13:15:33.460 INFO [stdout] 
Dec 01 13:15:33.460 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 13:15:33.460 INFO [stdout] 
Dec 01 13:15:33.460 INFO [stderr]      Running /target/debug/deps/unspecialized-2f6898152fbf4feb
Dec 01 13:15:33.462 INFO [stdout] 
Dec 01 13:15:33.462 INFO [stdout] running 0 tests
Dec 01 13:15:33.462 INFO [stdout] 
Dec 01 13:15:33.462 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 13:15:33.462 INFO [stdout] 
Dec 01 13:15:33.464 INFO [stderr] su: No module specific data is present
Dec 01 13:15:33.720 INFO running `"docker" "inspect" "229957bdf95003b8ff07cb79f602974a3e7db12e75dd6536e1c0cf40d5f7a413"`
Dec 01 13:15:33.800 INFO running `"docker" "rm" "-f" "229957bdf95003b8ff07cb79f602974a3e7db12e75dd6536e1c0cf40d5f7a413"`
Dec 01 13:15:33.892 INFO [stdout] 229957bdf95003b8ff07cb79f602974a3e7db12e75dd6536e1c0cf40d5f7a413
